This week's SwiftLee Weekly covers:

• Raw Identifiers in Swift
• Using a WebView in SwiftUI
• Using App Intents correctly

Enjoy this week's SwiftLee Weekly!

THIS WEEK'S BLOG POST

​Swift Computed Property: Code Examples​

While this is a basic in Swift, there are some nice additions since recently. For example, you can now use async and typed throws in the getter of a Swift computed property.

SPONSORED

​Full iOS coverage. Fast​

If your test suite is missing critical flows or isn’t up to date, you’re at risk of bugs slipping through. QA Wolf builds and maintains E2E tests that cover 80%+ of your iOS app in just weeks. Every test runs on real iPhones and iPads in parallel, so results reflect exactly what your users will experience. Ship your next iOS release with confidence, with QA Wolf — Schedule a demo.

SWIFT EVOLUTION

An overview of last week's Swift Proposal state changes. Check them out when they're in review, as it's your opportunity to influence the direction of Swift's future.

WHAT I'M WORKING ON

Finalizing macOS Tahoe and planning ahead

While it's always guessing the exact date of release, macOS and iOS will soon receive their final update for version 26. Being prepared means an opportunity to get featured by Apple, especially if you tick the boxes for recent features.

This year, that obviously means adopting the new design. RocketSim is pretty much ready for that, we're only beta testing the fundamental rewrite and improvements. (Join the beta here!)

Since the past months have been a huge focus on this major release, I haven't had the time to plan ahead. With a holiday planned, Q4 will approach soon. Planning has been the main driver of my success, especially when time was limited for side projects while having a full time job. I'd say it's crucial to ensure you focus on the right things.

For RocketSim, that means optimizing towards higher conversions. Our B2B part is growing way faster than expected, but also comes with challenges like support Single Sign-On (SSO). We have product market fit, but we need to optimize what we already offer. That means narrowing down a big list of tickets to just a realistic set of goals for Q4.

I'm using GitHub issues combined with a project board for this. No specific estimations, but a strict selection of tickets spread across both public and private repositories. (I explain this process in detail on going-indie.com). A productive quarter ahead, I wish you all the best for this week!

​